- 
                Notifications
    You must be signed in to change notification settings 
- Fork 1.1k
Add a delay after rtc_set_datetime #2156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a delay after rtc_set_datetime #2156
Conversation
| ping @armandomontanez - any idea why the CMake build is passing but the Bazel build is failing? | 
| Looks like you need to add  | 
| @peterharperuk can you fix merge conflicts and i'll re-review | 
7249c74    to
    f26fe7a      
    Compare
  
    | Apologies. Merge conflicts fixed. And I squashed everything together. | 
| Ah, not sure if this is fixed in different issue but you have added  
 | 
f26fe7a    to
    dce3159      
    Compare
  
    | I've tried to make the changes you suggested. You'll have to tell me how to test aon timer in a host build. | 
dce3159    to
    c3a3e12      
    Compare
  
    If you call rtc_get_datetime immediately after rtc_set_datetime you get junk back. According to the datasheet "Writing to the RTC will take 2 clk_rtc clock periods to arrive". So add a delay after calling rtc_set_datetime in aon_timer_set_time_calendar. Fixes raspberrypi#2148
c3a3e12    to
    f32bfca      
    Compare
  
    | 
 | 
If you call rtc_get_datetime immediately after rtc_set_datetime you get junk back. According to the datasheet "Writing to the RTC will take 2 clk_rtc clock periods to arrive". So add a delay after calling rtc_set_datetime in aon_timer_set_time_calendar. Fixes raspberrypi#2148
If you call rtc_get_datetime immediately after rtc_set_datetime you get junk back. According to the datasheet "Writing to the RTC will take 2 clk_rtc clock periods to arrive". So add a delay after calling rtc_set_datetime in aon_timer_set_time_calendar.
Fixes #2148